System, method, and apparatus for maintaining and updating a common message user interface in a group based communication system

ABSTRACT

Embodiments of the present disclosure provide methods, systems, apparatuses, and computer program products for maintaining and updating a common message user interface (UI) shared among a plurality of group-based communication interfaces in a group-based communication system. The common message UI is rendered based on an updated version or a most up-to-date state of the common message UI when accessed by a client device associated with one of the plurality of group-based communication interfaces.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/988,787, titled “SYSTEM, METHOD, AND APPARATUS FOR MAINTAINING ANDUPDATING A COMMON MESSAGE USER INTERFACE IN A GROUP BASED COMMUNICATIONSYSTEM,” filed May 24, 2018, the entire contents of which areincorporated herein by reference.

BACKGROUND

Various messaging systems are available that allow users to exchangemessages to conduct continuous device enabled conversations. Applicanthas identified a number of deficiencies and problems associated withconventional message exchanging systems. Through applied effort,ingenuity, and innovation, many of these identified problems have beensolved by developing solutions that are included in embodiments of thepresent disclosure, many examples of which are described in detailherein.

BRIEF SUMMARY

This specification relates to maintaining and updating a common messageuser interface (UI) shared among a plurality of group-basedcommunication interface elements in a group-based communication system.In one embodiment, a computing entity or apparatus is configured toreceive a group-based message generating request from an externalapplication. In the embodiment, the group-based message generatingrequest is associated with a common message UI that is configured to berendered within a selected group-based communication interface elementof the plurality of group-based communication interface elements. Theapparatus is further configured to generate, using a processor, a commonmessage UI identifier and a common message UI payload. In theembodiment, the common message UI identifier is stored to a commonmessage UI repository in association with the common message UI payload.The apparatus is further configured to receive user interaction dataassociated with an additional group-based communication interfaceelement of the plurality of group-based communication interface elementsfrom a client device. The apparatus is further configured to parse,using the processor, the user interaction data to identify a commonmessage UI accessing event. In the embodiment, the common message UIaccessing event is associated with the external application and thecommon message UI identifier.

In circumstances where the common message UI accessing event isidentified among user interaction data, the apparatus is furtherconfigured to retrieve, using the processor, the common message UIpayload from the common message UI repository using the common messageUI identifier. Finally, the apparatus is further configured to render,to the client device, the common message UI within the additionalgroup-based communication interface element based on the common messageUI payload.

In another embodiment, the apparatus is optionally configured totransmit, to the external application, a group-based message generatingresponse in response to the group-based message generating request. Inthe embodiment, the group-based message generating response comprisesthe common message UI identifier. The apparatus is optionally configuredto receive a common message UI update event associated with the commonmessage UI identifier from the external application or the clientdevice. The apparatus is optionally configured to store an updatedcommon message UI payload to the common message UI repository inassociation with the common message UI identifier.

The apparatus is optionally configured to transmit, using the processor,a common message UI update notification to the plurality of group-basedcommunication interface elements associated with the common message UIidentifier. In the embodiment, the common message UI update notificationcomprises the common message UI identifier. In the embodiment, thecommon message UI update notification is transmitted in parallel or in aselected order to the plurality of group-based communication interfaceelements. The selected order is associated with a most recent accesstime of the common message UI for each group-based communicationinterface element.

The apparatus is optionally configured to determine, using theprocessor, whether the common message UI update notification isreceived. In circumstances where the common message UI accessing eventis identified among the user interaction data and the common message UIupdate notification is received, the apparatus is optionally configuredto retrieve, using the processor, the updated common message UI payloadfrom the common message UI repository using the common message UIidentifier. Finally, the apparatus is optionally configured to render,to the client device, the common message UI within the additionalgroup-based communication interface element based on the updated commonmessage UI payload.

In another embodiment, the apparatus is optionally configured to receivea common message UI removal event associated with the common message UIidentifier from the external application or the client device. Theapparatus is optionally configured to remove, using the processor, thecommon message UI payload from the common message UI repository isassociation with the common message UI identifier.

The apparatus is optionally configured to determine whether the commonmessage UI identifier is associated with at least one of the pluralityof group-based communication interface elements. In circumstances wherethe common message UI identifier is determined to be not associated withany one of the plurality of group-based communication interfaceelements, the apparatus is optionally configured to remove, using theprocessor, the common message UI payload from the common message UIrepository in association with the common message UI identifier after atime period.

In another embodiment, before retrieving, using the processor, thecommon message UI payload from the common message UI repository usingthe common message UI identifier, the apparatus is optionally configuredto validate, using the processor, whether the client device isauthorized to access the common message UI payload. The apparatus isoptionally configured to determine, using the processor, whether thecommon message UI identifier associated with the common message UIpayload is generated.

In embodiments, each of the plurality of group-based communicationinterface elements is a channel list pane, a channel messaging pane, aflexpane, a message, a channel, or a dashboard.

Other embodiments include corresponding systems, methods, and computerprograms, configured to perform the operations of the apparatus, encodedon computer storage devices. The details of one or more embodiments ofthe subject matter described in this specification are set forth in theaccompanying drawings and the description below. Other features,aspects, and advantages of the subject matter will become apparent fromthe description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the disclosure in general terms, reference willnow be made to the accompanying drawings, which are not necessarilydrawn to scale, and wherein:

FIG. 1 is a system architecture diagram of a group-based communicationsystem configured to practice embodiments of the present disclosure;

FIG. 2 is an exemplary schematic diagram of a group-based communicationserver, according to one embodiment of the present disclosure;

FIG. 3 illustrates an exemplary common message UI shared among agroup-based communication channel and a flexpane, according to oneembodiment of the present disclosure;

FIG. 4 illustrates an exemplary common message UI shared or forwarded toanother group-based communication channel and another flexpane,according to one embodiment of the present disclosure;

FIG. 5 illustrates an exemplary updated common message UI shared among aplurality of group-based communication channels and flexpanes, accordingto one embodiment of the present disclosure;

FIG. 6 illustrates an exemplary flow diagram for generating andrendering a common message UI within an additional group-basedcommunication interface element, according to one embodiment of thepresent disclosure;

FIG. 7 illustrates an exemplary flow diagram for maintaining andrendering an updated common message UI within the additional group-basedcommunication interface element, according to one embodiment of thepresent disclosure;

FIG. 8 illustrates an exemplary flow diagram for removing a commonmessage UI payload from a common message UI repository after a commonmessage UI removal event, according to one embodiment of the presentdisclosure; and

FIG. 9 illustrates an exemplary flow diagram for removing a commonmessage UI payload from a common message UI repository after a timeperiod, according to one embodiment of the present disclosure.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments of the present disclosure now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the disclosure are shown. Indeed, thedisclosure may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

Overview

Various embodiments of the disclosure generally relate to a method formaintaining and updating a common message UI shared among a plurality ofgroup-based communication interface elements in a group-basedcommunication system. According to the present disclosure, a commonmessage UI identifier and a common message UI payload are generated fordisplaying a common message UI within a plurality of group-basedcommunication interface elements associated with an externalapplication. In embodiments, whenever a common message UI payload isassociation with the common message UI identifier is changed (such asbeing updated to a new version or being removed from a common message UIrepository), all of the group-based communication interface elementssharing the common message UI may be changed accordingly.

Instead of storing the updated common message UI payload to a memory ora database that is associated with a selected group-based communicationinterface element initiating the update event, in the presentdisclosure, the updated common message UI payload may be maintained,updated and stored to a common message UI repository. By way of thepresent disclosure, a global or common state of the common message UImay be shared among multiple group-based communication interfaceelements based on the common message UI identifier and the commonmessage UI payload. In embodiments, a common message UI identifier isintroduced and used as a pointer to locate the current or the mostup-to-date common message UI payload stored in the common message UIrepository for later accessing. By utilizing the relation of the commonmessage UI identifier and the actual memory address for storing thecurrent version of the common message UI payload, embodiments of thepresent disclosure resolve the issue of updating a common message UIwithin a selected group-based communication interface element, whileautomatically updating the common message UI within a plurality ofgroup-based communication interface elements associated with the samecommon message UI identifier.

Definitions

As used herein, the terms “data,” “content,” “digital content,” “digitalcontent object,” “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present disclosure.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present disclosure. Further, where acomputing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like, sometimes referred to herein as a “network.”Similarly, where a computing device is described herein to send data toanother computing device, it will be appreciated that the data may besent directly to another computing device or may be sent indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like.

The term “client device” refers to computer hardware and/or softwarethat is configured to access a service made available by a server. Theserver is often (but not always) on another computer system, in whichcase the client device accesses the service by way of a network. Clientdevices may include, without limitation, smart phones, tablet computers,laptop computers, wearables, personal computers, enterprise computers,and the like.

“Group-based” is used herein to refer to a system, channel, message, orvirtual environment that has security sufficient such that it isaccessible only to a defined group of users. The group may be defined bycommon access credentials such as those of an organization or commercialenterprise. Access may further be facilitated by a validated request tojoin or an invitation to join transmitted by one group member user toanother non-member user. Group identifiers (defined below) are used toassociate data, information, messages, etc., with specific groups.

The term “group-based communication system” refers to a communicationssoftware platform and associated hardware that is configured to supportand maintain a plurality of group-based communication interfaces and allassociated functionality. Group-based communication system users areorganized into organization groups (e.g., employees of differentcompanies may be separate organization groups) and each group interactswith the system via a respective group-based communication interface.For example, the group-based communication system might support, amongothers, a Slack Corporation group-based communication interface and anACME Corporation group-based communication interface. Examplegroup-based communication systems comprise supporting servers, clientdevices, and third party resources.

The term “group-based communication interface” refers to a virtualcommunications environment configured to facilitate user interactionwith a group-based communications system. Each group-based communicationinterface is accessible and viewable to a select group of users, such asa group of employees of a business or organization (e.g., the SlackCorp. interface would be accessible and viewable to the Slack employeeshowever the ACME Corporation group-based communication interface wouldnot be accessible and viewable to Slack employees). The group-basedcommunication interface includes a plurality of group-basedcommunication channels (e.g., a marketing channel, sales channel,accounting channel, etc.), which are defined below.

The term “group-based communication interface element” refers to adefined area in a group-based communication interface where informationis displayed. A group-based communication interface may be configured bya plurality of group-based communication interface elements, such as achannel list pane, a channel messaging pane, a flexpane, a message, achannel, or a dashboard. A “channel list pane” is a display paneconfigured to display lists of group-based communication channels and/orthreads that are configured to indicate when new messagingcommunications are received in the respective threads and/or group-basedcommunication channels. The channel list pane may include actuators forinitiating requests to view selected group-based communication channelsand/or a summary of selected threads. The channel list pane may includeadditional information, such as messaging communication information,notifications, the name of the group, name of the particular memberviewing the interface, etc. A “channel messaging pane” is a display paneconfigured to display a selected group-based communication channel andmay display a variety of information and a variety of messagesassociated with message UIs, notifications, actuators, andindicators/indications. A “flexpane” is a display pane that isconfigured to display digital contents that is associated with thechannel messaging pane, such as a selected thread. The flexpane mayinclude a variety of information, such as messaging communicationinformation, and may include a variety of actuators for initiatingrequests. The term “selected group-based communication interfaceelement” refers to a group-based communication interface elementselected for displaying a message UI (defined below) that is associatedwith or attached to a group-based message (defined below) communicatedwithin a selected group, a selected channel, or a selected organization.The term “additional group-based communication interface element” refersto another group-based communication interface element selected andadded for displaying the same message UI (defined below) that isassociated with or attached to another group-based message (definedbelow) communicated within an additional group, an additional channel,or an additional organization.

The term “group-based communication channel” refers to a virtualcommunications environment or feed that is configured to displaygroup-based messages posted by channel members (e.g., validated usersaccessing the environment using client devices) that are viewable onlyto the members of the group. The format of the group-based communicationchannel may appear differently to different members of the group-basedcommunication channel; however, the content of the group-basedcommunication channel (i.e., group-based messages) will be displayed toeach member of the group-based communication channel. For instance, acommon set of group-based messages will be displayed to each member ofthe respective group-based communication channel such that the contentof the group-based communication channel (i.e., group-based messages)will not vary per member of the group-based communication channel.

The terms “group-based communication channel identifier” or “channelidentifier” refer to one or more items of data by which a group-basedcommunication channel may be identified. For example, a group-basedcommunication channel identifier may comprise ASCII text, a pointer, amemory address, and the like.

The terms “group identifier” or “team identifier” refer to one or moreitems of data by which a group within a group-based communication systemmay be identified. For example, a group identifier may comprise ASCIItext, a pointer, a memory address, and the like.

The terms “organization identifier” or “business identifier” refer toone or more items of data by which an organization entity or a businessentity (e.g., employees of each company may be a separateorganization/business) within a group-based communication system may beidentified. For example, an organization identifier may comprise ASCIItext, a pointer, a memory address, and the like.

A “sending user identifier” is associated with a collection of messagesthat are sent by a particular user (i.e., a client device associatedwith the particular user). These messages may be analyzed to determinecontext regarding the user (e.g., the user's expertise or interest in atopic may be determined based on the frequency of mention of the topicor key words associated with the topic within such messages).

The term “user” should be understood to refer to an individual, group ofindividuals, business, organization, and the like; the users referred toherein are accessing a group-based communication or messaging systemusing client devices.

The terms “user profile,” “user account,” and “user account details”refer to information associated with a user, including, for example, auser identifier, one or more group-based communication channelidentifiers associated with group-based communication channels that theuser has been granted access to, one or more group identifiers forgroups with which the user is associated, one or more organizationidentifiers for organizations with which the user is associated, one ormore third party resource provider identifiers indicating whether aclient device associated with the user profile is authorized to accessrespective one or more third party resources, an indication as towhether the user is an owner of any group-based communication channels,an indication as to whether the user has any group-based communicationchannel restrictions, a plurality of messages, an emoji, a plurality ofconversations, a plurality of conversation topics, an avatar, an emailaddress, a real name (e.g., John Doe), a username (e.g., jdoe), apassword, a real name, a time zone, a status, and the like. The useraccount details can include a subset designation of user credentials,such as, for example, login information for the user including theuser's username and password.

As used herein, the terms “group-based message” and “message” refer toany electronically generated data or digital content object provided bya user using a client device and that is configured for display within agroup-based communication channel. Message communications may includeany text, image, video, audio or combination thereof provided by a user(using a client device). For instance, the user may provide agroup-based message that includes text as well as an image and a videowithin the group-based message as message contents. In such a case, thetext, image, and video would comprise the group-based message or digitalcontent object. Each message sent or posted to a group-basedcommunication channel of the group-based communication system includesmetadata comprising the following: a sending user identifier, a messageidentifier, message contents, a group identifier, and a group-basedcommunication channel identifier. Each of the foregoing identifiers maycomprise ASCII text, a pointer, a memory address, and the like.

Group-based communication system users are organized into organizationgroups (e.g., employees of each company may be a separate organizationgroup) and each organization group may access a group-basedcommunication interface having one or more group-based communicationchannels (explained below) to which users may be assigned or which theusers may join (e.g., group-based communication channels may representdepartments, geographic locations such as offices, product lines, userinterests, topics, issues, and/or the like). A group identifier may beused to facilitate access control for a message (e.g., access to themessage, such as having the message return as part of search results inresponse to a search query, may be restricted to those users having thegroup identifier associated with their user profile). The groupidentifier may be used to determine context for the message (e.g., adescription of the group, such as the name of an organization and/or abrief description of the organization, may be associated with the groupidentifier).

Group-based communication system users may join group-basedcommunication channels. Some group-based communication channels may beglobally accessible to those users having a particular organizationalgroup identifier associated with their user profile (i.e., users who aremembers of the organization). Access to some group-based communicationchannels may be restricted to members of specified groups, whereby thegroup-based communication channels are accessible to those users havinga particular group identifier associated with their user profile. Thegroup-based communication channel identifier may be used to facilitateaccess control for a message (e.g., access to the message, such ashaving the message return as part of search results in response to asearch query, may be restricted to those users having the group-basedcommunication channel identifier associated with their user profile, orwho have the ability to join the group-based communication channel). Thegroup-based communication channel identifier may be used to determinecontext for the message (e.g., a description of the group-basedcommunication channel, such as a description of a project discussed inthe group-based communication channel, may be associated with thegroup-based communication channel identifier).

The term “private group-based communication channel” refers to agroup-based communication channel with restricted access such that it isnot generally accessible and/or searchable by other members of thegroup-based communication system. For example, only those users oradministrators who have knowledge of and permission to access (e.g., agroup-based communication channel identifier for the private group-basedcommunication channel is associated with their user profile after theuser has been validated/authenticated) the private group-basedcommunication channel may view content of the private group-basedcommunication channel.

The term “user interaction data” refers to data generated based on userinteraction with one or more of the client devices. For example, userinteraction data may be generated based on group-based messages, inputs,uploads, or other user engagement of a group-based communicationinterface.

The term “external application” refers to a software program, platform,or service that is configured to communicate with the group-basedcommunication system for providing service to a client device via agroup-based communication interface. The external application operateson a compiled code base or repository that is separate and distinct fromthat which supports the group-based communication system. In someembodiments, the external application may communicate with thegroup-based communication system, and vice versa, through one or moreapplication program interfaces (APIs). In some embodiments, the externalapplication receives tokens or other authentication credentials that areused to facilitate secure communication between the external applicationand the group-based communication system in view of group-basedcommunication system network security layers or protocols (e.g., networkfirewall protocols). Once connected with the remote network device, theexternal application may transmit messages through the group-basedcommunication system to a targeted client device.

As used herein, the term “message user interface (UI)” refers to anelectronically generated platform that, when rendered for display on aclient device, provides information associated with a messagecommunicated within the group-based communication system. The message UIenables a user operating the client device to interact or communicatewith a server, a processing device, a program, or an externalapplication provided for a group-based communication user interfaceelement of a group-based communication system. For example, the messageUI may be in a form of an attachment that is attached to a messagecommunicated within a group-based communication channel. In such anexample, the message UI may be displayed under the message enabling auser operating the client device to interact or communicate with aserver, a processing device, a program, or an external applicationassociated with the message. In another example, the message UI may bein the form of threaded messages that is attached to a topic thread. Inanother example, the message UI may be mounted within a user dashboardfor rendering user profile or user account details.

The term “common message UI” refers to a message UI that is shared amonga plurality of group-based communication interface elements. Forexample, a common message UI may be shown within a first group-basedcommunication interface element associated with a first group-basedcommunication channel. In such an example, the same common message UImay later be forwarded and shared to a second group-based communicationinterface element associated with a second group-based communicationchannel.

The term “common message UI payload” refers to any data or digitalcontent that is associated with a common message UI that, when renderedto a client device, generates the common message UI. The common messageUI payload may be any data associated with the intended digital contentof the common message UI, or templates or instructions associated withthe common message UI. The term “updated common message UI payload”refers to a common message UI payload that is updated by an externalapplication or a client device in association with the common message UIidentifier (defined below). The updated common message UI payloadincludes a new or modified version of digital content based on theoriginal common message UI payload.

As used herein, the term “group-based message generating request” refersto an electronically generated request from an external application forgenerating group-based messages associated with a common message UI tobe rendered within multiple group-based communication interfaceelements, such as a channel messaging pane or a flexpane. Inembodiments, the generated group-based messages may be associated withthe same common message UI that is shared among multiple group-basedcommunication interface elements.

As used herein, the term “common message UI identifier” refers to one ormore items of data by which a common message UI memory address of acommon message UI repository (defined below) may be identified. Thecommon message UI repository is configured to store a common message UIpayload associated with a common message UI that is shared among aplurality of group-based communication interface elements. For example,a common message UI identifier may comprise ASCII text, a pointer, amemory address, and the like.

As used herein, the term “common message UI repository” refers to amemory or a database that is associated with common message UIidentifiers used for identifying or tracking an electronically generatedcommon message UI memory address of the memory or the database storingthe common message UI payload. The common message UI memory address maybe defined by bytes. For example, the common message UI memory addressmay be a binary address defined by an ordered and finite sequence ofbinary numbers that holds up to one byte. In such an example, the commonmessage UI identifier allows a processor to track, based on the one bytesequence of binary numbers, the common message UI memory address wherethe common message UI payload is stored within.

As used herein, the term “group-based message generating response”refers to an electronically generated response from a group-basedcommunication server that may provide data associated with thegroup-based messages to the external application initiating thegroup-based message generating request. A group-based message generatingresponse may include the common message UI identifier that is generatedfor locating a common message UI memory address in a common message UIrepository.

The term “common message UI accessing event” refers to an action,incident, collection of steps, or processes executed, via a clientdevice, by a user associated with a group-based communication interfaceelement for accessing a common message UI that is identifiable by aserver and may be correlated to one or more external applications.Accessing events may be pre-defined (e.g., button clicks, slashcommands, etc.) or may be learned by the group-based communicationsystem over time using machine learning models or other similartechniques. In example embodiments, once a common message UI accessingevent is identified, the group-based communication server is configuredto retrieve a common message UI identifier associated with the commonmessage UI to be accessed, locate the common message UI payload storedin the common message UI repository based on the retrieved commonmessage UI identifier, and retrieve and render for display the commonmessage UI payload stored in the common message UI repository.

The term “common message UI update event” refers to an action, incident,collection of steps, or processes executed, via a client device, by auser associated with a group-based communication interface element forupdating a common message UI that is identifiable by a server and may becorrelated to one or more external applications. The term may also referto an action, incident, collection of steps, or processes executed, viaan external application server, by an external application provider forupdating a common message UI that is identifiable by a server and may beshared among group-based communication interface elements. Update eventsmay be pre-defined (e.g., button clicks, slash commands, etc.) or may belearned by the group-based communication system over time using machinelearning models or other similar techniques. In example embodiments,once a common message UI update event is identified, the group-basedcommunication server is configured to transmit a common message UIupdate notification (defined below) comprising the common message UIidentifier to multiple group-based communication interface elementsassociated with the same common message UI identifier. In embodiments,the common message UI update notification may be transmitted in parallelor in a selected order based on a most recent access time associatedwith each group-based communication interface element.

It should be appreciated that the term “in parallel” refers tocircumstances where two or more events occur within a time period thatis less than, often considerably less than, a time period that would berequired if such events occurred sequentially or in series. The term “inparallel” is not used in an absolute sense and does not require thatevents or tasks occur in an identical or precisely synchronized timeperiod. For example, if two messages generated in parallel by twocomputing entities, then such messages are generated in a time periodthat is less than that which would be required if such messages weregenerated sequentially. In order words, the time period needed togenerate the first message is at least partly coextensive with (andoften substantially overlaps) the time period needed to generate thesecond message.

The term “access time” refers to an electronic record of time (e.g., atimestamp) representing the time when a client device associated with agroup-based communication interface element initiated a common messageUI accessing event by way of sending user interaction data to agroup-based communication server for accessing the common message UI.The group-based communication server, when received the user interactiondata, may parse the user interaction data to identify a common messageUI accessing event and an access time associated with the common messageUI for the group-based communication interface element. The term “mostrecent access time” refers to an electronic record of time (e.g., atimestamp) representing the latest access time when a client deviceassociated with a group-based communication interface element initiateda common message UI accessing event for accessing the common message UI.

The term “common message UI update notification” refers to anelectronically generated notification from a group-based communicationserver that may provide the common message UI identifier associated withan updated common message UI payload to all group-based communicationinterface elements associated with the common message UI identifier forupdating the original common message UI payload to a current version forlater accessing events initiated by client devices.

The term “common message UI removal event” refers to an action,incident, collection of steps, or processes executed, via a clientdevice, by a user associated with a group-based communication interfaceelement for removing or deleting a common message UI that isidentifiable by a server and may be correlated to one or more externalapplications. The term may also refer to an action, incident, collectionof steps, or processes executed, via an external application server, byan external application provider for removing a common message UI thatis identifiable by a server and shared among multiple group-basedcommunication interface elements. Removal events may be pre-defined(e.g., button clicks, slash commands, etc.) or may be learned by thegroup-based communication system over time using machine learning modelsor other similar techniques. In example embodiments, once a commonmessage UI removal event is identified, the group-based communicationserver is configured to remove the current common message UI payloadfrom the common message UI repository in associated with the commonmessage UI identifier.

Example System Architecture

Methods, apparatuses, and computer program products of the presentdisclosure may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a networked device (e.g., an enterpriseplatform), such as a server or other network entity, configured tocommunicate with one or more devices, such as one or more clientdevices. Additionally or alternatively, the computing device may includefixed computing devices, such as a personal computer or a computerworkstation. Still further, example embodiments may be embodied by anyof a variety of mobile devices, such as a portable digital assistant(PDA), mobile telephone, smartphone, laptop computer, tablet computer,wearable, or any combination of the aforementioned devices.

FIG. 1 illustrates an example computing system 100 within whichembodiments of the present disclosure may operate. Users may access agroup-based communication system 105 via a communications network 104using client devices 101A-101N. An external application server 108 mayinteract with a group-based communication system 105 via acommunications network 104. The group-based communication system 105 maycomprise a group-based communication server 106 in communication with atleast one group-based communication repository 107.

Communications network 104 may include any wired or wirelesscommunication network including, for example, a wired or wireless localarea network (LAN), personal area network (PAN), metropolitan areanetwork (MAN), wide area network (WAN), or the like, as well as anyhardware, software and/or firmware required to implement it (such as,e.g., network routers, etc.). For example, communications network 104may include a cellular telephone, an 802.11, 802.16, 802.20, and/orWiMax network. Further, the communications network 104 may include apublic network, such as the Internet, a private network, such as anintranet, or combinations thereof, and may utilize a variety ofnetworking protocols now available or later developed including, but notlimited to TCP/IP based networking protocols. For instance, thenetworking protocol may be customized to suit the needs of thegroup-based communication system. In some embodiments, the protocol is acustom protocol of JSON objects sent via a Websocket channel. In someembodiments, the protocol is JSON over RPC, JSON over REST/HTTP, and thelike.

The group-based communication server 106 may be embodied as a computeror computers as known in the art. The group-based communication server106 may provide for receiving of electronic data from various sources,including but not necessarily limited to the client devices 101A-101N orthe external application server 108. For example, the group-basedcommunication server 106 may be operable to receive and post or transmitgroup-based messages provided by the client devices 101A-101N or theexternal application server 108.

The group-based communication repository 107 may be embodied as a datastorage device such as a Network Attached Storage (NAS) device ordevices, or as a separate database server or servers. The group-basedcommunication repository 107 includes information accessed and stored bythe group-based communication server 106 to facilitate the operations ofthe group-based communication system 105. For example, the group-basedcommunication repository 107 may include, without limitation, aplurality of messaging communications organized among a plurality ofgroup-based communication channels, and/or the like.

The client devices 101A-101N may be any computing device as definedabove. Electronic data received by the group-based communication server106 from the client devices 101A-101N may be provided in various formsand via various methods. For example, the client devices 101A-101N mayinclude desktop computers, laptop computers, smartphones, netbooks,tablet computers, wearables, and the like.

In embodiments where a client device 101A-101N is a mobile device, suchas a smart phone or tablet, the client device 101A-101N may execute an“app” to interact with the group-based communication system 105. Suchapps are typically designed to execute on mobile devices, such astablets or smartphones. For example, an app may be provided thatexecutes on mobile device operating systems such as iOS®, Android®, orWindows®. These platforms typically provide frameworks that allow appsto communicate with one another and with particular hardware andsoftware components of mobile devices. For example, the mobile operatingsystems named above each provide frameworks for interacting withlocation services circuitry, wired and wireless network interfaces, usercontacts, and other applications. Communication with hardware andsoftware modules executing outside of the app is typically provided viaapplication programming interfaces (APIs) provided by the mobile deviceoperating system.

Additionally or alternatively, the client device 101A-101N may interactwith the group-based communication system 105 via a web browser. As yetanother example, the client device 101A-101N may include varioushardware or firmware designed to interface with the group-basedcommunication system 105.

In some embodiments of an exemplary group-based communication system105, a message or a group-based message may be sent from a client device101A-101N to a group-based communication system 105. In variousimplementations, the message may be sent to the group-basedcommunication system 105 over communications network 104 directly by aclient device 101A-101N, the message may be sent to the group-basedcommunication system 105 via an intermediary such as a message server,and/or the like. For example, the client device 101A-101N may be adesktop, a laptop, a tablet, a smartphone, and/or the like that isexecuting a client application (e.g., a group-based communication app).In one implementation, the message may include data such as a messageidentifier, sending user identifier, a group identifier, a group-basedcommunication channel identifier, message contents (e.g., text, emojis,images, links), attachments (e.g., files), message hierarchy data (e.g.,the message may be a reply to another message), third party metadata,and/or the like. In one embodiment, the client device 101A-101N mayprovide the following example message, substantially in the form of a(Secure) Hypertext Transfer Protocol (“HTTP(S)”) POST message includingeXtensible Markup Language (“XML”) formatted data, as provided below:

POST /authrequest.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <auth_request>  <timestamp>2020-12-31 23:59:59</timestamp> <user_accounts_details>   <user_account_credentials>   <user_name>ID_user_1</user_name>    <password>abc123</password >   //OPTIONAL <cookie>cookieID</cookie>    //OPTIONAL<digital_cert_link>www.mydigitalcertificate.com/JohnDoeDaDoeDoe@gmail.com/mycertifcate.dc</digital_cert_link>   //OPTIONAL <digital_certificate>_DATA_</digital_certificate>  </user_account_credentials>  </user_accounts_details> <client_details>//i0S Client with App and Webkit    //it should benoted that although several client details    //sections are provided toshow example variants of client    //sources, further messages willinclude only on to save    //space   <client_IP>10.0.0.123</client_IP>  <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 like MacOS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201Safari/9537.53</user_agent_string>  <client_product_type>iPhone6,1</client_product_type>  <client_serial_number>DNXXX1X1XXX</client_serial_number>  <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_ UDID>  <client_OS>i0S</client_OS>  <client_OS_version >7.1.1</client_OS_version >   <client_app_type>appwith webkit</client_app_type>  <app_installed_flag>true</app_installed_flag>  <app_name>NickName.app</app_name>   <app_version>1.0 </app_version>  <app_webkit_name>Mobile Safari</client_webkit_name>  <client_version>537.51.2</client_version>  </client_details> <client_details>//i0S Client with Webbrowser  <client_IP>10.0.0.123</client_IP>   <user_agent_string>Mozilla/5.0(iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML,like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string>  <client_product_type>iPhone6,1</client_product_type>  <client_serial_number>DNXV(1X1XXX1X1XXXX</client_serial_number>  <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_ UDID>  <client_OS>i0S</client_OS>   <client_OS_version >7.1.1</client_OS_version >   <client_app_type>web browser</client_app_type>  <client_name>Mobile Safari</client_name>  <client_version>9537.53</client_version>  </client_details> <client_details>//Android Client with Webbrowser  <client_IP>10.0.0.123</client_IP>   <user_agent_string>Mozilla/5.0(Linux; U; Android 4.0.4; en-us; Nexus S Build/IMM76D)AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 MobileSafari/534.30</user_agent_string>   <client_product_type>NexusS</client_product_type>  <client_serial_number>YXXXXXXXXZ</client_serial_number>  <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID>  <client_OS>Android</client_OS>  <client_OS_version>4.0.4</client_OS_version>   <client_app_type>webbrowser</client_app_type>   <client_name>Mobile Safari</client_name>  <client_version>534.30</client_version>  </client_details> <client_details>//Mac Desktop with Webbrowser  <client_IP>10.0.0.123</client_IP>   <user_agent_string>Mozilla/5.0(Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.75.14 (KHTML, likeGecko) Version/7.0.3 Safari/537.75.14</user_agent_string>  <client_product_type>MacPro5,1</client_product_type>  <client_serial_number>YXXXXXXXXZ</client serial number>  <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID>  <client_OS>Mac OS X</client_OS>  <client_OS_version>10.9.3</client_OS_version>   <client_app_type>webbrowser</client_app_type>   <client_name>Mobile Safari</client_name>  <client_version>537.75.14</client_version>  </client_details> <message>   <message_identifier>ID_message_10</message_identifier>  <team_identifier>ID_team_1</team_identifier>  <channel_identifier>ID_channel_1</channel_identifier>   <contents>Thatis an interesting invention. I have attached a copy our patentpolicy.</contents>   <attachments>patent_policy.pdf</attachments> </message> </auth_request>

The group-based communication system 105 comprises at least onegroup-based communication server 106 that may create a storage messagebased upon the received message to facilitate message indexing andstorage in a group-based communication repository 107. In oneimplementation, the storage message may include data such as a messageidentifier, a group identifier, a group-based communication channelidentifier, a sending user identifier, topics, responses, messagecontents, attachments, message hierarchy data, third party metadata,conversation primitive data, and/or the like. For example, thegroup-based communication server 106 may provide the following examplestorage message, substantially in the form of a HTTP(S) POST messageincluding XML-formatted data, as provided below:

-   -   POST/storage_message.php HTTP/1.1    -   Host: www.server.com    -   Content-Type: Application/XML    -   Content-Length: 667    -   <?XML version=“1.0” encoding=“UTF-8”?>    -   <storage_message>        -   <message_identifier>ID_message_10</message_identifier>        -   <team_identifier>ID_team_1</team_identifier>        -   <channel_identifier>ID_channel_1</channel_identifier>        -   <sending_user_identifier>ID_user_1</sending_user_identifier>        -   <topics>            -   <topic>inventions</topic>            -   <topic>patents</topic>            -   <topic>policies</topic>        -   </topics>        -   <responses>            -   <response>liked by ID_user_2</response>            -   <response>starred by ID_user_3</response>        -   </responses>        -   <contents>That is an interesting invention. I have attached            a copy our patent policy.</contents>        -   <attachments>patent_policy.pdf</attachments>        -   <conversation_primitive>            -   conversation includes messages: ID_message_8,                ID_message_9, ID_message_10, ID_message_11,                ID_message_12        -   </conversation_primitive>    -   </storage_message>

In embodiments, a group identifier as defined above may be associatedwith the message.

In embodiments, a group-based communication channel identifier asdefined above may be associated with the message.

In embodiments, a sending user identifier as defined above may beassociated with the message. In one implementation, the message may beparsed (e.g., using PHP commands) to determine a sending user identifierof the user who sent the message.

In embodiments, topics may be associated with the message. In oneimplementation, the message contents may be parsed (e.g., using PHPcommands) to determine topics discussed in the message. For example,hashtags in the message may channels associated with the message. Inanother example, the message may be analyzed (e.g., by itself, withother messages in a conversation primitive) or parsed using a machinelearning technique, such as topic modeling, to determine topicsassociated with the message.

In embodiments, data indicating responses may be associated with themessage. For example, responses to the message by other users mayinclude reactions (e.g., selection of an emoji associated with themessage, selection of a “like” button associated with the message),clicking on a hyperlink embedded in the message, replying to the message(e.g., posting a message to the group-based communication channel inresponse to the message), downloading a file associated with themessage, sharing the message from one group-based communication channelto another group-based communication channel, pinning the message,starring the message, and/or the like. In one implementation, dataregarding responses to the message by other users may be included withthe message, and the message may be parsed (e.g., using PHP commands) todetermine the responses. In another implementation, data regardingresponses to the message may be retrieved from a database. For example,data regarding responses to the message may be retrieved via a MySQLdatabase command similar to the following:

-   -   SELECT messageResponses    -   FROM MSM_Message    -   WHERE messagelD=ID_message_10.

For example, data regarding responses to the message may be used todetermine context for the message (e.g., a social score for the messagefrom the perspective of some user). In another example, data regardingresponses to the message may be analyzed to determine context regardingthe user (e.g., the user's expertise in a topic may be determined basedon the responses to the user's message regarding the topic).

In embodiments, message UIs, such as attachments, may be included withthe message. If there are attachments, files may be associated with themessage. In one implementation, the message may be parsed (e.g., usingPHP commands) to determine file names of the attachments. For example,file contents may be analyzed to determine context for the message(e.g., a patent policy document may indicate that the message isassociated with the topic “patents”).

In embodiments, third party metadata may be associated with the message.For example, third party metadata may provide additional contextregarding the message or the user that is specific to a company, group,group-based communication channel, and/or the like. In oneimplementation, the message may be parsed (e.g., using PHP commands) todetermine third party metadata. For example, third party metadata mayindicate whether the user who sent the message is an authorizedrepresentative of the group-based communication channel (e.g., anauthorized representative may be authorized by the company to respond toquestions in the group-based communication channel).

In embodiments, a conversation primitive may be associated with themessage. In one implementation, a conversation primitive is an elementused to analyze, index, store, and/or the like messages. For example,the message may be analyzed by itself, and may form its own conversationprimitive. In another example, the message may be analyzed along withother messages that make up a conversation, and the messages that makeup the conversation may form a conversation primitive. In oneimplementation, the conversation primitive may be determined as themessage, a specified number (e.g., two) of preceding messages and aspecified number (e.g., two) of following messages. In anotherimplementation, the conversation primitive may be determined based onanalysis of topics discussed in the message and other messages (e.g., inthe channel) and/or proximity (e.g., message send order proximity,message send time proximity) of these messages.

In embodiments, various metadata, determined as described above, and/orthe contents of the message may be used to index the message (e.g.,using the conversation primitive) to facilitate various facets ofsearching (i.e., search queries that return results from group-basedcommunication repository 107). In one implementation, a storage messagemay be sent from group-based communication server 106 to facilitateindexing in group-based communication repository 107. In anotherimplementation, metadata associated with the message may be determinedand the message may be indexed in group-based communication repository107. In one embodiment, the message may be indexed such that a company'sor a group's messages are indexed separately (e.g., in a separate indexassociated with the group and/or company that is not shared with othergroups and/or companies). In one implementation, messages may be indexedat a separate distributed repository (e.g., to facilitate data isolationfor security purposes).

If there are attachments associated with the message, file contents ofthe associated files may be used to index such files in group-basedcommunication repository 107 to facilitate searching. In one embodiment,the files may be indexed such that a company's or a group's files areindexed at a separate distributed repository.

Example Apparatus for Implementing Embodiments of the Present Disclosure

FIG. 2 illustrates an exemplary schematic diagram of a group-basedcommunication server 200 that may be embodied by one or more computingsystems. The group-based communication server 200 may include aprocessor 202, a memory 201, input/output circuitry 203, communicationscircuitry 205, and common message UI maintaining and updating circuitry204. The group-based communication server 200 may be configured toexecute the operations described herein. Although the components aredescribed with respect to functional limitations, it should beunderstood that the particular implementations necessarily include theuse of particular hardware. It should also be understood that certain ofthe components described herein may include similar or common hardware.For example, two sets of circuitry may both leverage use of the sameprocessor, network interface, storage medium, or the like to performtheir associated functions, such that duplicate hardware is not requiredfor each set of circuitry. The use of the term “circuitry” as usedherein with respect to components of the apparatus should therefore beunderstood to include particular hardware configured to perform thefunctions associated with the particular circuitry as described herein.

The term “circuitry” should be understood broadly to include hardwareand, in some embodiments, software for configuring the hardware. Forexample, in some embodiments, “circuitry” may include processingcircuitry, storage media, network interfaces, input/output devices, andthe like. In some embodiments, other elements of the group-basedcommunication server 200 may provide or supplement the functionality ofparticular circuitry. For example, the processor 202 may provideprocessing functionality, the memory 201 may provide storagefunctionality, the communications circuitry 205 may provide networkinterface functionality, and the like.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 201 via a bus forpassing information among components of the apparatus. The memory 201may be non-transitory and may include, for example, one or more volatileand/or non-volatile memories. In other words, for example, the memorymay be an electronic storage device (e.g., a computer readable storagemedium). The memory 201 may be configured to store information, data,content, applications, instructions, or the like, for enabling theapparatus to carry out various functions in accordance with exampleembodiments of the present disclosure.

The processor 202 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. Additionally or alternatively, the processor mayinclude one or more processors configured in tandem via a bus to enableindependent execution of instructions, pipelining, and/ormultithreading. The use of the term “processing circuitry” may beunderstood to include a single core processor, a multi-core processor,multiple processors internal to the apparatus, and/or remote or “cloud”processors.

In an example embodiment, the processor 202 may be configured to executeinstructions stored in the memory 201 or otherwise accessible to theprocessor. Alternatively, or additionally, the processor may beconfigured to execute hard-coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present disclosure while configured accordingly. Alternatively,as another example, when the processor is embodied as an executor ofsoftware instructions, the instructions may specifically configure theprocessor to perform the algorithms and/or operations described hereinwhen the instructions are executed.

In some embodiments, the group-based communication server 200 mayinclude input/output circuitry 203 that may, in turn, be incommunication with processor 202 to provide output to the user and, insome embodiments, to receive an indication of a user input. Theinput/output circuitry 203 may comprise a user interface and may includea display and may comprise a web user interface, a mobile application, aclient device, a kiosk, or the like. In some embodiments, theinput/output circuitry 203 may also include a keyboard, a mouse, ajoystick, a touch screen, touch areas, soft keys, a microphone, aspeaker, or other input/output mechanisms. The processor and/or userinterface circuitry comprising the processor may be configured tocontrol one or more functions of one or more user interface elementsthrough computer program instructions (e.g., software and/or firmware)stored on a memory accessible to the processor (e.g., memory 201, and/orthe like).

The communications circuitry 205 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the group-based communication server 200. In this regard, thecommunications circuitry 205 may include, for example, a networkinterface for enabling communications with a wired or wirelesscommunication network. For example, the communications circuitry 205 mayinclude one or more network interface cards, antennae, buses, switches,routers, modems, and supporting hardware and/or software, or any otherdevice suitable for enabling communications via a network. Additionallyor alternatively, the communication interface may include the circuitryfor interacting with the antenna(s) to cause transmission of signals viathe antenna(s) or to handle receipt of signals received via theantenna(s).

The common message UI maintaining and updating circuitry 204 includeshardware configured to support a group-based communication system. Thecommon message UI maintaining and updating circuitry 204 may utilizeprocessing circuitry, such as the processor 202, to perform theseactions. The common message UI maintaining and updating circuitry 204may send and/or receive data from group-based communication repository107. In some implementations, the sent and/or received data may be ofenterprise-based digital content objects organized among a plurality ofgroup-based communication channels. In some implementations, the sentand/or received data may be of enterprise-based digital content objectsto be rendered within a plurality of group-based communication interfaceelements. It should also be appreciated that, in some embodiments, thecommon message UI maintaining and updating circuitry 204 may include aseparate processor, specially configured field programmable gate array(FPGA), or application specific interface circuit (ASIC).

As described above and as will be appreciated based on this disclosure,embodiments of the present disclosure may be configured as methods,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions (e.g., computer software) embodied in the storagemedium. Any suitable computer-readable storage medium may be utilizedincluding non-transitory hard disks, CD-ROMs, flash memory, opticalstorage devices, or magnetic storage devices.

Example Processes for Maintaining and Updating a Common Message UserInterface (UI) in a Group-Based Communication System

FIG. 3 illustrates an exemplary common message UI shared among agroup-based communication channel 320 and a flexpane 330, according toone embodiment of the present disclosure. In embodiments, a group-basedcommunication interface 300 may comprise a plurality of group-basedcommunication interface elements, such as the channel list pane 310, achannel messaging pane 320 associated with the group-based communicationchannel 2, a flexpane 330 associated with a selected thread, group-basedmessages 320A-320D, or a dashboard such as a user dashboard comprisinguser profile data (not shown in FIG. 3). Each of the group-basedcommunication interface element may be displayed on client devices101A-101N. In embodiments, the message input field 303 may be providedwithin the channel messaging pane 320 or the flexpane 330, such that auser may interact or communicate with the group-based communicationserver 106 and a message UI may be generated based on the user'sinteraction or communication with the group-based communication server106. In embodiments the follow button 304 may be provided within theflexpane 330, such that a user may select to follow specific threadsthey are interested in.

As illustrated in FIG. 3, the group-based communication interface 300may be associated with different group-based communication channels(Channel 1-Channel 5) and are presented within the channel list pane 310on a display of client devices 101A-101N. Once a specific group-basedcommunication channel is selected based on user's interaction with thechannel list pane 310, the specific group-based communication channelmay be displayed within the channel messaging pane 320. For example,when a user interacted with the channel list pane 310 by clicking on theChannel 2 button 310A, group-based messages 320A-320C associated withChannel 2 may be rendered within the channel messaging pane 320. Inembodiments, threads associated with a selected group-based message mayfurther be displayed based on user's interaction with the flexpane 330.For example, when a user interacted with the channel list pane 310 byclicking on the group-based message 320C, threads associated with thegroup-based message 320C may be rendered within the flexpane 330.

Each group-based message displayed within the channel messaging pane 320may comprise group-based message information, which includes userinformation identifying a user who sent the group-based message, atimestamp indicating when the group-based message was sent, and amessage UI generated in a form of an attachment and displayed under thegroup-based message for providing information associated with themessage. For example, group-based message 320A includes user information“John Doe,” a timestamp “10:22 AM,” and a message UI 322A attached tothe group-based message 320A and comprising a text block showing “Doesanyone have the Word document for project A?” For another example,group-based message 320B includes user information “Jane Doe,” atimestamp “10:23 AM,” and a message UI 322B attached to the group-basedmessage 320B and comprising a text block showing “I do.” For anotherexample, group-based message 320C includes user information “Jane Doe,”a timestamp “10:25 AM,” and a message UI 322C attached to thegroup-based message 320C and comprising a text block showing “Here isthe Word file:,” a link to “Project A_v1.doc,” and a thread block 324Cindicating there is one reply to the group-based message 320C.

Threads displayed within the flexpane 330 may comprise the selectedgroup-based message and its related replying messages. For example,threads shown in FIG. 3 include the selected group-based message 320Dgenerated based on the original group-based message 320C and its relatedone replying message 324D Similarly, each selected group-based messageand its related replying messages may include the selected group-basedmessage information, which includes user information identifying a userwho sent the group-based message, a timestamp indicating when theselected group-based message was sent, and a message UI generated in aform of an attachment and displayed under the group-based message forproviding information associated with the message. For example, theselected group-based message 320D generated based on the originalgroup-based message 320C includes user information “Jane Doe,” atimestamp “10:25 AM,” and a message UI 322D attached to the group-basedmessage 320D and comprising a text block showing “Here is the Wordfile:,” a link to “Project A_v1.doc.” Further, the related replyingmessage is displayed and shown as 324D that includes user information“John Doe,” a timestamp “10:27 AM,” and a message UI 326D attached tothe selected group-based message 320D and comprising a text blockshowing “Thanks.”

In the exemplary embodiment, the group-based messages 320A-320D areuniformly rendered to each user viewing the group-based communicationinterface associated with the selected Channel 2. For the purposesdescribed herein, the user may interact or communicate with thegroup-based communication server 106 utilizing the message input field303. And a message UI may be generated based on the user's interactionor communication with the group-based communication server 106. Forexample, the user, John Doe using a client device may input or enter“Does anyone have the Word document for project A?” into the messageinput field 303. And based on the content John Doe keyed or entered, amessage UI 322A may be generated and rendered within the group-basedcommunication interface 300 by way of attaching a text block under theuser information or timestamp of the group-based messages 320A. Anotheruser, Jane Doe using another client device, when viewed the group-basedmessage 320A posted by John Doe, may input or enter “I do.” into themessage input field 303. Further, Jane Doe may input or enter “Here isthe Word file:” and upload the Word file “Project A_v1.doc” using themessage input field 303. And based on the content Jane Doe keyed orentered, a message UI 322C may be generated and rendered within thechannel messaging pane 320 associated with Channel 2 by way of attachingthe Word file “Project A_v1.doc” to a text block under the userinformation or timestamp of the group-based message 320C. Incircumstances where Jane Doe would like to share the same Word file fromChannel 2 to Channel 5, Jane Doe may forward the group-based message320C to another channel messaging pane 320 associated with Channel 5 toform the group-based message 320E as shown in FIG. 4.

FIG. 4 illustrates an exemplary common message UI shared or forwarded toanother group-based communication channel and another flexpane,according to one embodiment of the present disclosure. In theembodiment, group-based messages associated with a common message UI maybe shared among different group-based communication interface elements.For example, group-based messages associated with a common message UIcomprising a text block showing “Here is the Word file:” and a link to“Project A_v1.doc” may be shared between channel messaging panes andflexpanes that are associated with Channel 2 and Channel 5. In such anembodiment, the group-based messages 320C and 320D may be presented on adisplay of a client device that is associated with Channel 2, while thegroup-based messages 320E and 320F may be presented on a display ofanother client device that is associated with Channel 5. In such anembodiment, the group-based messages 320C, 320D, 320E, and 320F mayshare the common message UI (such as 322C, 322D, 322E, and 322F)comprising the same Word file: Project A_v1.doc as an attachment.

FIG. 5 illustrates an exemplary updated common message UI shared among aplurality of group-based communication channels and flexpanes, accordingto one embodiment of the present disclosure. In embodiments, user JohnDoe may upload a new version of the updated Word file as “ProjectA_v2.doc” using the message input field 303 within the channel messagingpane 320 associated with Channel 2. And based on the updated Word fileJohn Doe uploaded, an updated message UI 322G associated with theoriginal message UI 322C may be generated and rendered within thechannel messaging pane 320 associated with Channel 2 by way of attachingthe updated Word file “Project A_v2.doc” to a text block under the userinformation or timestamp of the group-based message 320G. According tothe embodiment of the present disclosure, group-based messages 320E and320F (illustrated in FIG. 4) that are shared and forwarded based on theoriginal common message UI 322C may be automatically associated with theupdated common message UI 322G comprising the updated Word file “ProjectA_v2.doc”. In the embodiment, when a client device associated withChannel 5 would like to access the Word file, the group-basedcommunication server 106 may automatically retrieve the updated commonmessage UI payload in a common message UI repository storing the updatedWord file “Project A_v2.doc,” and further render for display the updatedWord file “Project A_v2.doc” on the client device.

FIG. 6 illustrates an exemplary flow diagram for generating andrendering a common message UI within an additional group-basedcommunication interface element, according to one embodiment of thepresent disclosure. The method 600 begins with receiving a group-basedmessage generating request from an external application (601). Thegroup-based message generating request is associated with the commonmessage UI to be rendered within a selected group-based communicationinterface element of the plurality of group-based communicationinterface elements. In embodiments, the group-based communicationinterface element may be a channel list pane, a channel messaging pane,a flexpane, a message, a channel, or a dashboard that is associated withuser profile information.

The method 600 further continues with generating, using a processor 202,a common message UI identifier and a common message UI payload (602). Inembodiments, the common message UI identifier is stored to a commonmessage UI repository in association with the common message UI payload.For example, as shown in FIG. 3, group-based messages 320C and 320D areassociated with a common message UI (e.g., the Word file “ProjectA_v1.doc”). In such an example, a common message UI identifier and acommon message UI payload that are associated with the common message UI(e.g., the Word file “Project A_v1.doc”) are generated. In embodiments,a common message UI identifier is generated for identifying a memoryaddress in a common message UI repository for storing the common messageUI payload. The common message UI payload may include digital content ofthe Word file “Project A_v1.doc.”

The method 600 further continues with receiving, from a client device(e.g., 101A-101N), user interaction data associated with an additionalgroup-based communication interface element of the plurality ofgroup-based communication interface elements (603). The method 600further continues with parsing, using the processor, the userinteraction data to identify a common message UI accessing event (604).In embodiments, the common message UI accessing event is associated withthe external application and the common message UI identifier. Thecommon message UI accessing event may be identified among userinteraction data for determining whether the user engagement of theadditional group-based communication interface element is to access acommon message UI associated with the external application and thecommon message UI identifier.

In circumstances where the common message UI accessing event isidentified among the user interaction data (605), the method 600 furthercontinues with retrieving, using the processor 202, the common messageUI payload from the common message UI repository using the commonmessage UI identifier (606). For example, as illustrated in FIG. 3, theprocessor 202 may be used to retrieve the common message UI identifiergenerated for retrieving the common message UI payload (e.g., thedigital content of the Word file “Project A_v1.doc”) stored to thecommon message UI repository. Finally, the method 600 further continueswith rendering, to the client device (e.g., 101A-101N), the commonmessage UI within the additional group-based communication interfaceelement based on the common message UI payload (607). For example, asillustrated in FIG. 3, the common message UI payload (e.g., the digitalcontent of Word file “Project A_v1.doc”) may be rendered to a clientdevice operated by a user who initiated the common message UI accessingevent and is associated with Channel 2 or Channel 5.

In embodiments, before retrieving, using the processor 202, the commonmessage UI payload from the common message UI repository using thecommon message UI identifier, the method 600 optionally continues withvalidating, using the processor 202, whether the client device isauthorized to access the common message UI payload. And the method 600optionally continues with determining, using the processor 202, whetherthe common message UI identifier associated with the common message UIpayload is generated.

FIG. 7 illustrates an exemplary flow diagram for maintaining andrendering an updated common message UI within the additional group-basedcommunication interface element, according to one embodiment of thepresent disclosure. Following FIG. 6, the method 700 continues withtransmitting a group-based message generating response in response tothe group-based message generating request to the external application(701). In embodiments, the group-based message generating response maycomprise the common message UI identifier.

The method 700 continues with receiving, from the external application108 or the client device (e.g., 101A-101N), a common message UI updateevent associated with the common message UI identifier (702). Forexample, as shown in FIG. 5, a common message UI update event associatedwith the updated common message UI payload (e.g., the digital content ofWord file “Project A_v2.doc”) may be received from a client device. Insuch an example, the common message UI update event may be initiated byuser's interaction with a client device such as uploading the updatedcommon message UI (e.g., the Word file “Project A_v2.doc”) via themessage input field 303 within the channel messaging pane 320 associatedwith Channel 2.

The method 700 further continues with storing an updated common messageUI payload to the common message UI repository (703). For example, asillustrated in FIG. 5, the updated common message UI payload (e.g., thedigital content of Word file “Project A_v2.doc”) may be stored to thecommon message UI repository where the original common message UIpayload (e.g., the digital content of Word file “Project A_v1.doc”) isstored.

The method 700 further continues with transmitting, using the processor202, a common message UI update notification to the plurality ofgroup-based communication interface elements that are associated withthe common message UI identifier in parallel or in a selected order(704). In embodiments, the common message UI update notification maycomprise the common message UI identifier. In embodiments, the selectedorder may be associated with a most recent access time of the commonmessage UI for each group-based communication interface element. Forexample, a common message UI update notification comprising the commonmessage UI identifier (e.g., the common message UI identifier associatedwith the updated common message UI 322G comprising the updated Word file“Project A_v2.doc”) may be transmitted to Channel 2 and Channel 5 inparallel or in a selected order. In such an example, the common messageUI update notification may be broadcasted to Channel 2 and Channel 5substantially simultaneously. In such an example, the common message UIupdate notification may also be transmitted to Channel 2 and Channel 5based on a most recent access time of the common message UI (e.g., theWord file “Project A_v1.doc”) associated with each channel. For example,the common message UI update notification may be transmitted to Channel5 first, since the group-based message 320E has a timestamp showing themost recent access time of the common message UI (e.g., the Word file“Project A_v1.doc”) associated with Channel 5 is approximately at 10:30AM when a user clicked on the Word file “Project A_v1.doc” link. Then,the common message UI update notification may later be transmitted toChannel 2, since the group-based message 320C has a timestamp showingthe most recent access time of the common message UI (e.g., the Wordfile “Project A_v1.doc”) associated with Channel 2 is approximately at10:25 AM when a user clicked on the Word file “Project A_v1.doc” link.

The method 700 further continues with determining, using the processor202, whether the common message UI update notification is received(705). In circumstances where the common message UI accessing event isidentified among the user interaction data and the common message UIupdate notification is received (706), the method 700 further continueswith retrieving, using the processor 202, the updated common message UIpayload from the common message UI repository using the common messageUI identifier (707). For example, as illustrated in FIG. 4, when a userassociated with Channel 5 is intended to access the common message UIpayload (e.g., the digital content of Word file “Project A_v1.doc”) byclicking on the link shown within the common message UI 322E, theprocessor 202 may be used to retrieve the updated common message UIpayload (e.g., the digital content of Word file “Project A_v2.doc”)stored in the common message UI repository based on the common messageUI identifier shared between Channel 2 and Channel 5.

The method 700 finally continues with rendering, to the client device(e.g., 101A-101N), the common message UI within the additionalgroup-based communication interface element based on the updated commonmessage UI payload (708). For example, as illustrated in FIG. 4, afterthe original common message UI payload is being updated and uploaded,the updated common message UI payload (e.g., the digital content of Wordfile “Project A_v2.doc”) may be rendered to a client device operated bya user, associated with Channel 2 or Channel 5, who initiated the commonmessage UI accessing event to access the common message UI.

FIG. 8 illustrates an exemplary flow diagram for removing a commonmessage UI payload from a common message UI repository after a commonmessage UI removal event, according to one embodiment of the presentdisclosure. The method 800 begins with receiving, from the externalapplication 108 or the client device (e.g., 101A-101N), a common messageUI removal event associated with the common message UI identifier (801).The method 800 further continues with removing, using the processor 202,the common message UI payload from the common message UI repository inassociation with the common message UI identifier (802).

FIG. 9 illustrates an exemplary flow diagram for removing a commonmessage UI payload from a common message UI repository after a timeperiod, according to one embodiment of the present disclosure. Themethod 900 begins with determining, using the processor 202, whether thecommon message UI identifier is associated with at least one of theplurality of group-based communication interface elements (901). Incircumstances where the common message UI is determined to be notassociated with any one of the plurality of group-based communicationinterface elements (902), the method 900 further continues withremoving, using the processor 202, the common message UI payload fromthe common message UI repository in association with the common messageUI identifier after a time period (903).

Additional Implementation Details

Although an example processing system has been described in FIG. 2,implementations of the subject matter and the functional operationsdescribed herein can be implemented in other types of digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them.

Embodiments of the subject matter and the operations described hereincan be implemented in digital electronic circuitry, or in computersoftware, firmware, or hardware, including the structures disclosed inthis specification and their structural equivalents, or in combinationsof one or more of them. Embodiments of the subject matter describedherein can be implemented as one or more computer programs, i.e., one ormore modules of computer program instructions, encoded on computerstorage medium for execution by, or to control the operation of,information/data processing apparatus. Alternatively, or in addition,the program instructions can be encoded on an artificially-generatedpropagated signal, e.g., a machine-generated electrical, optical, orelectromagnetic signal, which is generated to encode information/datafor transmission to suitable receiver apparatus for execution by aninformation/data processing apparatus. A computer storage medium can be,or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially-generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (e.g., multiple CDs, disks, orother storage devices).

The operations described herein can be implemented as operationsperformed by an information/data processing apparatus oninformation/data stored on one or more computer-readable storage devicesor received from other sources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (application-specific integrated circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor information/data (e.g., one or more scripts stored in a markuplanguage document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub-programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described herein can be performed by oneor more programmable processors executing one or more computer programsto perform actions by operating on input information/data and generatingoutput. Processors suitable for the execution of a computer programinclude, by way of example, both general and special purposemicroprocessors, and any one or more processors of any kind of digitalcomputer. Generally, a processor will receive instructions andinformation/data from a read-only memory or a random access memory orboth. The essential elements of a computer are a processor forperforming actions in accordance with instructions and one or morememory devices for storing instructions and data. Generally, a computerwill also include, or be operatively coupled to receive information/datafrom or transfer information/data to, or both, one or more mass storagedevices for storing data, e.g., magnetic, magneto-optical disks, oroptical disks. However, a computer need not have such devices. Devicessuitable for storing computer program instructions and information/datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described herein can be implemented on a computer having adisplay device, e.g., a CRT (cathode ray tube) or LCD (liquid crystaldisplay) monitor, for displaying information/data to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described herein can be implemented ina computing system that includes a back-end component, e.g., as aninformation/data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a web browserthrough which a user can interact with an implementation of the subjectmatter described herein, or any combination of one or more suchback-end, middleware, or front-end components. The components of thesystem can be interconnected by any form or medium of digitalinformation/data communication, e.g., a communication network. Examplesof communication networks include a local area network (“LAN”) and awide area network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., an HTML page) toa client device (e.g., for purposes of displaying information/data toand receiving user input from a user interacting with the clientdevice). Information/data generated at the client device (e.g., a resultof the user interaction) can be received from the client device at theserver.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anydisclosures or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular disclosures.Certain features that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

CONCLUSION

Many modifications and other embodiments of the disclosures set forthherein will come to mind to one skilled in the art to which thesedisclosures pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the disclosures are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

The invention claimed is:
 1. An apparatus for outputting a commonmessage user interface (UI) shared among a plurality of group-basedcommunication interface elements in a group-based communication system,the apparatus comprising at least one processor and at least one memoryincluding computer program code, the at least one memory and thecomputer program code configured to, with the at least one processor,cause the apparatus to: receive first user interaction data associatedwith a selected group-based communication interface element of theplurality of group-based communication interface elements; parse thefirst user interaction data to identify a common message UI accessingevent associated with a common message UI identifier; in circumstanceswhere the common message UI accessing event is identified among thefirst user interaction data: retrieve a common message UI payload from acommon message UI repository using the common message UI identifier; andcause the common message UI to be rendered within the selectedgroup-based communication interface element based on the common messageUI payload; and receive second user interaction data associated with anadditional group-based communication interface element of the pluralityof group-based communication interface elements; parse the second userinteraction data to identify a second common message UI accessing event;in circumstances where a second common message UI accessing event isidentified among the second user interaction data: retrieve the commonmessage UI payload from the common message UI repository using thecommon message UI identifier; and cause the common message UI to berendered within the additional group-based communication interfaceelement based on the common message UI payload.
 2. The apparatus ofclaim 1, wherein the at least one memory and the computer program codeconfigured to, with the at least one processor, further cause theapparatus to: receive, from an external application, a group-basedmessage generating request associated with the common message UI to berendered within the selected group-based communication interface elementof the plurality of group-based communication interface elements; andtransmit, to the external application, a group-based message generatingresponse in response to the group-based message generating request, thegroup-based message generating response comprising the common message UIidentifier.
 3. The apparatus of claim 1, wherein the at least one memoryand the computer program code configured to, with the at least oneprocessor, further cause the apparatus to: receive, from an externalapplication or the client device, a common message UI removal eventassociated with the common message UI identifier; and remove, using theprocessor, the common message UI payload from the common message UIrepository is associated with the common message UI identifier.
 4. Theapparatus of claim 1, wherein the at least one memory and the computerprogram code configured to, with the at least one processor, furthercause the apparatus to: in circumstances where the common message UIidentifier is determined to be not associated with any one of theplurality of group-based communication interface elements: remove thecommon message UI payload from the common message UI repository inassociation with the common message UI identifier after a time period.5. The apparatus of claim 1, wherein the at least one memory and thecomputer program code configured to, with the at least one processor,further cause the apparatus to: validate whether the client device isauthorized to access the common message UI payload; and determinewhether the common message UI identifier associated with the commonmessage UI payload is generated.
 6. The apparatus of claim 1, whereineach of the plurality of group-based communication interface elementscomprises one or more of a channel list pane, a channel messaging pane,a flexpane, a message, a channel, or a dashboard.
 7. A method foroutputting a common message user interface (UI) shared among a pluralityof group-based communication interface elements in a group-basedcommunication system, the method comprising: receiving first userinteraction data associated with a selected group-based communicationinterface element of the plurality of group-based communicationinterface elements; parsing the first user interaction data to identifya common message UI accessing event associated with a common message UIidentifier; retrieving a common message UI payload from a common messageUI repository using the common message UI identifier; causing the commonmessage UI to be rendered within the selected group-based communicationinterface element based on the common message UI payload; receivingsecond user interaction data associated with an additional group-basedcommunication interface element of the plurality of group-basedcommunication interface elements; parsing the second user interactiondata to identify a second common message UI accessing event; retrievingthe common message UI payload from the common message UI repositoryusing the common message UI identifier; and causing the common messageUI to be rendered within the additional group-based communicationinterface element based on the common message UI payload.
 8. The methodof claim 7, further comprising: receiving, from an external application,a group-based message generating request associated with the commonmessage UI to be rendered within the selected group-based communicationinterface element of the plurality of group-based communicationinterface elements; and transmitting, to the external application, agroup-based message generating response in response to the group-basedmessage generating request, the group-based message generating responsecomprising the common message UI identifier.
 9. The method of claim 7,further comprising: receiving, from an external application or theclient device, a common message UI removal event associated with thecommon message UI identifier; and removing the common message UI payloadfrom the common message UI repository in association with the commonmessage UI identifier.
 10. The method of claim 7, further comprising: incircumstances where the common message UI is determined to be notassociated with any one of the plurality of group-based communicationinterface elements: removing the common message UI payload from thecommon message UI repository in association with the common message UIidentifier after a time period.
 11. The method of claim 7, furthercomprising: validating whether the client device is authorized to accessthe common message UI payload; and determining whether the commonmessage UI identifier associated with the common message UI payload isgenerated.
 12. The method of claim 7, wherein each of the plurality ofgroup-based communication interface elements comprises one or more of achannel list pane, a channel messaging pane, a flexpane, a message, achannel, or a dashboard.
 13. A computer program product for outputting acommon message user interface (UI) shared among a plurality ofgroup-based communication interface elements in a group-basedcommunication system, the computer program product comprising at leastone non-transitory computer-readable storage medium havingcomputer-readable program instructions stored thereon, thecomputer-readable program instructions, in execution with at least oneprocessor, configured to: receive first user interaction data associatedwith a selected group-based communication interface element of theplurality of group-based communication interface elements associatedwith a common message UI identifier; parse the first user interactiondata to identify a common message UI accessing event among the firstuser interaction data; retrieve a common message UI payload from acommon message UI repository using the common message UI identifier;cause the common message UI to be rendered within the selectedgroup-based communication interface element based on the common messageUI payload; receive second user interaction data associated with anadditional group-based communication interface element of the pluralityof group-based communication interface elements; parse the second userinteraction data to identify a second common message UI accessing event;retrieve the common message UI payload from the common message UIrepository using the common message UI identifier; and causing thecommon message UI to be rendered within the additional group-basedcommunication interface element based on the common message UI payload.14. The computer program product of claim 13, wherein thecomputer-readable program instructions, in execution with at least oneprocessor, are further configured to: receive, from an externalapplication, a group-based message generating request associated withthe common message UI to be rendered within the selected group-basedcommunication interface element of the plurality of group-basedcommunication interface elements; and transmit, to the externalapplication, a group-based message generating response in response tothe group-based message generating request, the group-based messagegenerating response comprising the common message UI identifier.
 15. Thecomputer program product of claim 13, wherein the computer-readableprogram instructions, in execution with at least one processor, arefurther configured to: receive, from an external application or theclient device, a common message UI removal event associated with thecommon message UI identifier; and remove, using the processor, thecommon message UI payload from the common message UI repository isassociated with the common message UI identifier.
 16. The computerprogram product of claim 13, wherein the computer-readable programinstructions, in execution with at least one processor, are furtherconfigured to: in circumstances where the common message UI identifieris determined to be not associated with any one of the plurality ofgroup-based communication interface elements: remove the common messageUI payload from the common message UI repository in association with thecommon message UI identifier after a time period.
 17. The computerprogram product of claim 13, wherein the computer-readable programinstructions, in execution with at least one processor, are furtherconfigured to, further configured to: validate whether the client deviceis authorized to access the common message UI payload; and determinewhether the common message UI identifier associated with the commonmessage UI payload is generated.
 18. The computer program product ofclaim 13, wherein each of the plurality of group-based communicationinterface elements comprises one or more of a channel list pane, achannel messaging pane, a flexpane, a message, a channel, or adashboard.